• alias.cfg

    From Bill McGarrity@VERT to All on Fri Nov 14 19:39:00 2014
    Once again.... a dilemma...

    I was lead to the understanding incoming email could be then posted to a sub using the sub:<intcode> in the alias.cfg. I have created a user called MTAINFO and signed up for a service that will send email TO: mtainfo@tequilamockingbirdonline.net. This service offersdifferent information using different sending addresses but all with the same host.

    In the alias.cfg I put the following line:

    MTAINFO sub:1nyctinfo

    When the email comes in addressed to mtainfo@tequilamockingbirdonline.net say from lirr@alerts.mta.info I get an error stating:

    1400 !SMTP lirr@alerts.mta.info (user #0) cannot post on NYCT/MTA Srv Information (Reason 690)

    SoI went a step further and added to alias.cfg:

    lirr@alerts.mta.info sub:1nyctinfo

    Same message.

    Does each email address need to have a user #?

    Thanks...








    Bill

    Telnet: bbs.tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    IRC:irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look TWICE... Save a LIFE!!! Motorcycles are Everywhere!!
    --- MultiMail/Win32 v0.50
    tequilamockingbirdonline.net
  • From Digital Man@VERT to Bill McGarrity on Fri Nov 14 19:39:00 2014
    Re: alias.cfg
    By: Bill McGarrity to All on Fri Nov 14 2014 07:50 pm

    Once again.... a dilemma...

    I was lead to the understanding incoming email could be then posted to a
    sub using the sub:<intcode> in the alias.cfg. I have created a user called MTAINFO and signed up for a service that will send email TO: mtainfo@tequilamockingbirdonline.net. This service offers different information using different sending addresses but all with the same host.

    In the alias.cfg I put the following line:

    MTAINFO sub:1nyctinfo

    When the email comes in addressed to mtainfo@tequilamockingbirdonline.net say from lirr@alerts.mta.info I get an error stating:

    1400 !SMTP lirr@alerts.mta.info (user #0) cannot post on NYCT/MTA Srv Information (Reason 690)

    So I went a step further and added to alias.cfg:

    lirr@alerts.mta.info sub:1nyctinfo

    Same message.

    Does each email address need to have a user #?

    No. Check the posting requirements you have set in SCFG for the sub-board with the internal code "1nyctinfo". I suspect your posting requirements are non-blank and therefore disallow an anonymous/unauthenticated SMTP agent from posting to the sub-board.

    digital man

    Synchronet "Real Fact" #78:
    172 Synchronet Match Maker registrations were sold (@$69) between 1995 and 1996.
    Norco, CA WX: 64.5F, 76.0% humidity, 4 mph SE wind, 0.00 inches rain/24hrs
    Synchronet Vertra
  • From Bill McGarrity@VERT to Digital Man on Sat Nov 15 01:40:00 2014
    On 11-14-14 17:39, Digital Man wrote to Bill McGarrity <=-


    Once again.... a dilemma...

    I was lead to the understanding incoming email could be then posted to a
    sub using the sub:<intcode> in the alias.cfg. I have created a user called MTAINFO and signed up for a service that will send email TO: mtainfo@tequilamockingbirdonline.net. This service offers different information using different sending addresses but all with the same host.

    In the alias.cfg I put the following line:

    MTAINFO sub:1nyctinfo

    When the email comes in addressed to mtainfo@tequilamockingbirdonline.net say from lirr@alerts.mta.info I get an error stating:

    1400 !SMTP lirr@alerts.mta.info (user #0) cannot post on NYCT/MTA Srv Information (Reason 690)

    So I went a step further and added to alias.cfg:

    lirr@alerts.mta.info sub:1nyctinfo

    Same message.

    Does each email address need to have a user #?

    No. Check the posting requirements you have set in SCFG for the
    sub-board with the internal code "1nyctinfo". I suspect your posting requirements arenon-blank and therefore disallow an anonymous/unauthenticated SMTP agent from posting to the sub-board.

    OK... what I found was the posting requirements was blank but the group access requirement was level 50. I created a new group and left everything blank and it works fine.

    Thanks again DM...


    Bill

    Telnet: bbs.tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look TWICE... Save a LIFE!!! Motorcycles are Everywhere!!
    --- MultiMail/Win32 v0.50
    tequilamockingbirdonline.net
  • From Digital Man@VERT to Bill McGarrity on Sat Nov 15 22:21:00 2014
    Re: Re: alias.cfg
    By: Bill McGarrity to Digital Man on Sat Nov 15 2014 02:19
    am

    On 11-14-14 17:39, Digital Man wrote to Bill McGarrity <=-


    Once again.... a dilemma...

    I was lead to the understanding incoming email could be then posted to a sub using the sub:<intcode> in the alias.cfg. I have created a user
    called MTAINFO and signed up for a service that will send email TO:
    mtainfo@tequilamockingbirdonline.net. This service offers different information using different sending addresses but all with the same
    host.

    In the alias.cfg I put the following line:

    MTAINFO sub:1nyctinfo

    When the email comes in addressedto
    mtainfo@tequilamockingbirdonline.net say from lirr@alerts.mta.info I get an error stating:

    1400 !SMTP lirr@alerts.mta.info (user #0) cannot post on NYCT/MTA Srv Information (Reason 690)

    So I went a step furtherand added to alias.cfg:

    lirr@alerts.mta.info sub:1nyctinfo

    Same message.

    Does each email address need to have a user #?

    No. Check the posting requirements you have set in SCFG for the sub-board withthe internal code "1nyctinfo". I suspect your posting requirements are non-blank and therefore disallow an anonymous/unauthenticated SMTP agent from posting to the sub-board.

    OK... what I found was the posting requirements was blank but the group access requirement was level 50. I created a new group and left everything blank and it works fine.

    Thanks again DM...

    Sure. You could also use requirements like "LEVEL 50 OR USER=0" to allow an authenticated user (e.g. SMTP agent) to have access.

    digital man

    Synchronet "Real Fact" #67:
    Robert D. Bouman, the author of SyncEdit, died in the mid to late 1990's. Norco, CA WX: 60.0F, 85.0% humidity, 7 mph ESE wind, 0.00 inches rain/24hrs
    Synchronet Vertrauen Home of Synchronet
  • From Bill McGarrity@VERT to Digital Man on Sat Nov 15 23:39:00 2014
    On 11-15-14 20:02, Digital Man wrote to Bill McGarrity <=-


    On 11-14-14 17:39, Digital Man wrote to Bill McGarrity <=-


    Once again.... a dilemma...

    I was lead to the understanding incoming email could be then posted to a sub using the sub:<intcode> in the alias.cfg. I have created a user called MTAINFO and signed up for a service that will send email TO: mtainfo@tequilamockingbirdonline.net. This service offers different information using different sending addresses but all with the same
    host.

    In the alias.cfg I put the following line:

    MTAINFO sub:1nyctinfo

    When the email comes in addressed to
    mtainfo@tequilamockingbirdonline.net say from lirr@alerts.mta.info I get an error stating:

    1400 !SMTP lirr@alerts.mta.info (user #0) cannot post on NYCT/MTA Srv Information (Reason 690)

    So I went a step further and added to alias.cfg:

    lirr@alerts.mta.info sub:1nyctinfo

    Same message.

    Does each email address need to have a user #?

    No. Check the posting requirements you have set in SCFG for the
    sub-board with the internal code "1nyctinfo". I suspect your posting requirements are non-blank and therefore disallow an anonymous/unauthenticated SMTP agent fromposting to the sub-board.

    OK... what I found was the posting requirements was blank but the group access requirement was level 50. I created a new group and left everything blank and it works fine.

    Thanks again DM...

    Sure. You could also use requirements like "LEVEL 50 OR USER=0" to
    allow an authenticated user (e.g. SMTP agent) to have access.

    Good to know... I'll try that as well... :)


    Bill

    Telnet: bbs.tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look TWICE... Save a LIFE!!! Motorcycles are Everywhere!!
    --- MultiMail/Win32 v0.50
    tequilamockingbirdonline.net
  • From Digital Man@VERT to Bill McGarrity on Thu Nov 27 09:59:00 2014
    Re: Re: alias.cfg
    By: Bill McGarrity to Digital Man on Sat Nov 15 2014 02:19
    am

    On 11-14-14 17:39, Digital Man wrote to Bill McGarrity <=-


    Once again.... a dilemma...

    I was lead to the understanding incoming email could be then posted to a sub using the sub:<intcode> in the alias.cfg. I have created a user
    called MTAINFO and signed up for a service that will send email TO:
    mtainfo@tequilamockingbirdonline.net. This service offers different information using different sending addresses but all with the same
    host.

    In the alias.cfg I put the following line:

    MTAINFO sub:1nyctinfo

    When the email comes in addressedto
    mtainfo@tequilamockingbirdonline.net say from lirr@alerts.mta.info I get an error stating:

    1400 !SMTP lirr@alerts.mta.info (user#0) cannot post on NYCT/MTA Srv Information (Reason 690)

    So I went a step furtherand added to alias.cfg:

    lirr@alerts.mta.info sub:1nyctinfo

    Same message.

    Does each email address need to have a user #?

    No. Check the posting requirements you have set in SCFG for the sub-board withthe internal code "1nyctinfo". I suspect your posting requirements are non-blank and therefore disallow an anonymous/unauthenticated SMTP agent from posting to the sub-board.

    OK... what I found was the posting requirements was blank but the group access requirement was level 50. I created a new group and left everything blank and it works fine.

    Thanks again DM...

    Sure. You could also use requirements like "LEVEL 50 OR USER=0" to allow an authenticated user (e.g. SMTP agent) to have access.

    digital man

    Synchronet "Real Fact" #67:
    Robert D. Bouman, the author of SyncEdit, died in the mid to late 1990's. Norco, CA WX: 60.0F, 85.0% humidity, 7 mph ESE wind, 0.00 inches rain/24hrs
    Synchronet Vertrauen Home of Syn