AREPLY - error for external addresses.

cwr9

posted Dec 27 '14 at 4:18 am

Hi -

Sorry to re-open an old thread, but I'm having a similar issue with auto-replies, and changing ISP's isn't an option...

I've been using the same ISP for 14 yrs, and it does relay as long as "any" validly formatted e-mail address is in the MAIL FROM field when sending an outgoing message - just apparently not when the MAIL FROM field is empty (<>) as I've found out recently when attempting to use auto-reply.

Hoping to get more insight into why the MAIL FROM <> response doesn't contain a valid user.

Based on the help file info - MercuryC / Forced SMTP sender - it sounds like we should be able to always have a valid MAIL FROM user sent to the outgoing server for validation.

I've tried changing various settings, including adding various headers via outgoing rules for the AutoReply message that don't appear to be included by default in auto-replies ( Return-Path:, From:, Resent-from:, X-AutoForwarded: ) as well as adding the forced smtp sender, etc.

I guess my expected behavior, for auto-replies, would be for MercuryC to use either the "receiving" mail account name as the "MAIL FROM<>" account when sending the auto-reply, or use the postmaster / forced smtp sender account in the MAIL FROM<> field.

Is there something I am missing / some way to cause MercuryC to always populate the MAIL FROM, and / or any way to add the MAIL FROM user via outgoing rules (it's not a header, but is typically taken from the Return-Path or From field I believe).

Oh - and i can include a full connection log from my server to my ISP for an auto-reply if needed, but the relevant issue field is the same as Dave shows above - the empty MAIL FROM:<> response

22:25:28.265: << MAIL FROM:<> SIZE=676<cr><lf>

Thanks for any help anyone can give.

Chad

Hi - Sorry to re-open an old thread, but I'm having a similar issue with auto-replies, and changing ISP's isn't an option... I've been using the same ISP for 14 yrs, and it does relay as long as "any" validly formatted e-mail address is in the MAIL FROM field when sending an outgoing message - just apparently not when the MAIL FROM field is empty (&lt;&gt;) as I've found out recently when attempting to use auto-reply. Hoping to get more insight into why the MAIL FROM &lt;&gt; response doesn't contain a valid user.Based on&nbsp; the help file info - MercuryC / Forced SMTP sender&nbsp; - it sounds like we should be able to always have a valid MAIL FROM user sent to the outgoing server for validation.I've tried changing various settings, including adding various headers via outgoing rules for the AutoReply message that don't appear to be included by default in auto-replies ( Return-Path:, From:, Resent-from:, X-AutoForwarded: ) as well as adding the forced smtp sender, etc. I guess my expected behavior, for auto-replies, would be for MercuryC to use either the "receiving" mail account name as the "MAIL FROM&lt;&gt;" account when sending the auto-reply, or use the postmaster / forced smtp sender account in the MAIL FROM&lt;&gt; field.Is there something I am missing / some way to cause MercuryC to always populate the MAIL FROM, and / or any way to add the MAIL FROM user via outgoing rules (it's not a header, but is typically taken from the Return-Path or From field I believe). Oh - and i can include a full connection log from my server to my ISP for an auto-reply if needed, but the relevant issue field is the same as Dave shows above - the empty MAIL FROM:&lt;&gt; response 22:25:28.265: &lt;&lt; MAIL FROM:&lt;&gt; SIZE=676&lt;cr&gt;&lt;lf&gt; Thanks for any help anyone can give.Chad

Leizure

posted Aug 9 '10 at 2:30 pm

I've searched the forum for an answer but can't find one so hopefully someone can point me in the right direction!

I have placed an areply.pm file in a user's mailbox and it works fine for local mail. However, all non-local mail errors with:

---

The attached message has failed delivery and has been referred to you as postmaster. The following error report or reports were given to explain the problem:

*** leizure@leizure.force9.co.uk
550 relaying mail to leizure.force9.co.uk is not allowed

---

I did have 'strict local relaying' ticked but I've now removed that and just have 'do not permit SMTP relaying of local mail'.

Therefore, as I understand the help file, any locally sent email to a non-local address will be accepted.

The email is being sent from the local system using the user's email address as the FROM address so why does it not send?

Config is: 4.72 ::

# MERCURY.INI generated by Mercury Setup
#
#
# Sample Bindery Mode MERCURY.INI file (in fact, the one I use on
# my production server). This one implements most of the possible
# switches for each module, but you can edit it to do less if you
# wish. All the fields shown below are described in the file
# MGUIDE.HLP which is supplied in the Mercury archive.
#
# Anything after a '#' to the end of the line is a comment and
# is stripped out before parsing. Trailing and leading whitespace
# is also stripped before parsing. Many sample commands have been
# left in this file commented out for reference purposes.
#

[General]
myname:          mydomain # Canonical name for this server
timezone:        +0000    # Time Zone to add to date fields
file_api:        1    # Use the file api instead of queues
mailqueue:       C:\MERCURY\QUEUE    # Where mail should be put for delivery
smtpqueue:       C:\MERCURY\QUEUE    # Where the SMTP client should look for mail
newmail_path:    C:\MERCURY\MAIL\~N    # Where to find the users' WinPMail mailboxes.

[Protocols]
MERCURYS.DLL
MERCURYP.DLL
# MERCURYE.DLL
MERCURYC.DLL
MERCURYD.DLL
# MERCURYH.DLL
# MERCURYF.DLL
MERCURYW.DLL
# MERCURYX.DLL
MERCURYI.DLL
MERCURYB.DLL

[Mercury]
failfile:      C:\MERCURY\Mercury\FAILURE.MER    # Delivery failure notification template
confirmfile:   C:\MERCURY\Mercury\CONFIRM.MER    # Delivery confirmation template
aliasfile:     C:\MERCURY\Mercury\ALIAS.MER    # System-wide alias file
synfile:       C:\MERCURY\Mercury\SYNONYM.MER    # User synonym database
listfile:      C:\MERCURY\Mercury\LISTS.MER    # List of lists
logfile:       D:\Mlogs\Syslog.log    # Traffic logging file
logwidth:      30    # Width of address fields in logfile
retpath:       1    # Do/Don't use 'return-path' for errors
maxhops:       30    # Used to detect mailing loops
gullible:      1    # If NZ, don't validate 'From' fields
bitnethost:    cunyvm.cuny.edu    # Relay host for '.bitnet' rewrites
poll:          10   # Seconds between queue polling cycles
scratch:       D:\Mlogs\Scratch    # Where we can write temp files
returnlines:   15    # How many lines of failed messages to return
postmaster:    dwi    # NetWare UIC of postmaster
broadcast:     1    # Yes, we want broadcast notifications, but
receipts:      0    # ... no broadcasts for receipt confirmations
PM_notify:     1    # Do/Don't send errors to the postmaster
change_owner: 1    # Change message ownership to recipient
auto_tzone:    1    # If NZ, obtain timezone information from OS
LogLevel:      15    # System message reporting level
LogMax:        100    # Maximum number of system messages to store
RetryPeriod:   30    # Period between job retries (minutes)
MaxRetries:    16    # Maximum number of times a job can fail
TwoPasses:     1    # If NZ, process submission queue in 2 passes
Autoaddress:   7    # If NZ, auto-generate user addresses based on name
Daily_exit:    0    # If NZ, auto-restart each day after maintenance
No_Areply:     0    # If NZ, disable automatic replies system-wide
Alt_Forward:   0    # If NZ, allow alternate forwarding specification
Maint_hour:    2    # Hour for daily maintenance (24-hour clock)
Maint_min:     0    # Minute for daily maintenance
Retry_Mode:    0    # If NZ, use progressive backoff for queue retries
Local_DSNs:    1    # If NZ generate Delivery Status for local users only
DSN_time1:     10800    # Seconds deferred before first DSN is sent
DSN_time2:     86400    # Seconds deferred before second DSN is sent
DSN_time3:     259200    # Seconds deferred before third DSN is sent
Host_in_title: 0    # If NZ, show hostname in system tray and taskbar
Lingering:     0    # Enable or disable 'lingering mailboxes'
Linger_Timeout: 60   # Seconds before a lingering mailbox is shut down
Alert_Host:    notify.pmail.com    # Host to check for licensee advisories
Alert_Interval: 720   # Frequency in minutes (min 240) for checks
Alert_Flags:   0    # Flags controlling advisory checks
Alert_Users:   dwi    # Local users to receive advisories

[MercuryC]
Host : smtp.ntltelewestbusiness.co.uk
Failfile : C:\MERCURY\Mercury\FAILURE.MER
Poll : 10
Scratch : C:\MERCURY\Mercury
ReturnLines : 15
Timeout : 240
ESMTP : 1
POP3_Auth : 0
Logfile : d:\Mlogs\logs\smtprelayclient
Log_Verbose : 1
Session_logging : d:\Mlogs\logs\smtprelayclient
Session_logmode : 1

[MercuryE]
HELO : Baylis Mail Server
Session_logging : d:\mlogs\SMTPCSD
Session_logmode : 0
Poll : 15
Timeout : 60
Nameservers : 10.51.4.220
Logfile : d:\mlogs\SMTPCL.log
Log_Verbose : 0
DNS_Timeout : 20
DNS_Retries : 4
Transcripts : 1
MaxThreads : 10

[MercuryD]
Scratch : C:\MERCURY\Mercury
Timeout : 100
Poll : 30
Session_logging : d:\Mlogs\POPCSL.log
Session_logmode : 0

[MercuryS]
Debug : 1
Logfile : D:\Mlogs\MERCURYS.LOG
Timeout : 60
Relay : 0
Strict_Relay : 0
8BitMime : 1
Allow_Illegals : 0
SMTP_Authentication : 1
Auth_File : smtp_auth.txt
Session_logging : D:\Mlogs\SMTPServ
Session_logmode : 1
Compliance_Settings : 944
Maximum_Failed_Rcpts : 15
Max_Relay_Attempts : 4
SSL_Mode : 0
ST_Blacklisting : 288
No_VRFY : 0
SMTP_ConnFlags : 0
Compliance_Exceptions : restrictOK.txt

[MercuryP]
Scratch : C:\MERCURY\Mercury
Logfile : d:\Mlogs\pop3s.log
Stack : 32768
Mark_Read : 1
SSL_Mode : 0
Login_Disabled : 0
UIDL_nul_list : 1
New_UIDs : 0
No_NUL_passwords : 0
Session_logging : d:\Mlogs\POP3SSD
Session_logmode : 0
Timeout : 60

[MercuryX]
Cmd_Wait: 1
IE4_Dialling: 0
Use_ETRN: 0
Clients_only: 0
Drain_queues: 1
Sunday: 0000,0400,5000,0,0,0
Monday: 0000,0400,5000,0,0,0
Tuesday: 0000,0400,5000,0,0,0
Wednesday: 0000,0400,5000,0,0,0
Thursday: 0000,0400,5000,0,0,0
Friday: 0000,0400,5000,0,0,0
Saturday: 0000,0400,5000,0,0,0

[Domains]
mydomains

[Maiser]
Maiser:          Maiser   # 'Username' of mail server account
Helpfile:        C:\MERCURY\Mercury\MAISER.HLP   # Help sent on failed maiser requests
Lookupfile:      C:\MERCURY\Mercury\MAISER.LKP   # Format file for the 'lookup' command
Send_dir:        C:\MERCURY\Mercury\SENDABLE   # Directory for the 'send' command
Logfile:         D:\Mlogs\MAISER.LOG   # Mail server log file
Notify:          C:\MERCURY\Mercury\TMP   # Dir. for pending 'notify' commands
NoList:          N   # If 'Y', disable the 'list' command
Local_only:      Y   # If 'Y', local 'notify' commands only

[MercuryH]
Logfile : C:\MERCURY\Logs\MERCURYH.LOG
# Addressbook : \\CLIO\SYS\SYSTEM\MERCURY\PH.PMR
# MOTD : \\CLIO\SYS\SYSTEM\MERCURY\PH-MOTD.TXT
# Administrator : postmaster@clio.pmail.gen.nz
Timeout : 30

[MercuryI]
Scratch : C:\MERCURY\SCRATCH
Logfile : d:\Mlogs\imapl.log
Timeout : 120
Server_Port : 143
SSL_Port: 993
Charset : ISO-8859-1
Session_logging : d:\Mlogs\imapsd
Session_logmode : 0
Idle_Timeout : 1800
SSL_Mode : 0
Login_Disabled : 0
No_NUL_passwords : 1

[MercuryB]
Scratch : C:\MERCURY\SCRATCH
Timeout : 120
Server_Port : 81
Idle_Timeout : 1800
URL_Base : 10.51.4.10
SSL_Mode : 0
Alt_Server_Port : 443

[Groups]

[Rewrite]

[Statistics]
StatFlags:    16 # Statistical reporting settings
STF_Hours:    24 # How often to write stat log files
STM_Hours:    24 # How often to e-mail stat log files

I've searched the forum for an answer but can't find one so hopefully someone can point me in the right direction! &nbsp;I have placed an areply.pm file in a user's mailbox and it works fine for local mail. However, all non-local mail errors with: ---&nbsp; &nbsp;The attached message has failed delivery and has been referred to you as postmaster. The following error report or reports were given to explain the problem: &nbsp;&nbsp; *** <A href="mailto:leizure@leizure.force9.co.uk">leizure@leizure.force9.co.uk</A> &nbsp;&nbsp; 550 relaying mail to leizure.force9.co.uk is not allowed ---&nbsp; I did have 'strict local relaying' ticked but I've now removed that and just have 'do not permit SMTP relaying of local mail'. Therefore, as I understand the help file, any locally sent email to a non-local address will be accepted. The email is being sent from the local system using the user's email address as the FROM address so why does it not send? Config is: 4.72 :: #&nbsp; MERCURY.INI generated by Mercury Setup # # #&nbsp; Sample Bindery Mode MERCURY.INI file (in fact, the one I use on #&nbsp; my production server). This one implements most of the possible #&nbsp; switches for each module, but you can edit it to do less if you #&nbsp; wish. All the fields shown below are described in the file #&nbsp; MGUIDE.HLP which is supplied in the Mercury archive. # #&nbsp; Anything after a '#' to the end of the line is a comment and #&nbsp; is stripped out before parsing. Trailing and leading whitespace #&nbsp; is also stripped before parsing. Many sample commands have been #&nbsp; left in this file commented out for reference purposes. # [General] myname:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mydomain # Canonical name for this server timezone:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +0000&nbsp;&nbsp;&nbsp; # Time Zone to add to date fields file_api:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # Use the file api instead of queues mailqueue:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\MERCURY\QUEUE&nbsp;&nbsp;&nbsp; # Where mail should be put for delivery smtpqueue:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\MERCURY\QUEUE&nbsp;&nbsp;&nbsp; # Where the SMTP client should look for mail newmail_path:&nbsp;&nbsp;&nbsp; C:\MERCURY\MAIL\~N&nbsp;&nbsp;&nbsp; # Where to find the users' WinPMail mailboxes. [Protocols] MERCURYS.DLL MERCURYP.DLL # MERCURYE.DLL MERCURYC.DLL MERCURYD.DLL # MERCURYH.DLL # MERCURYF.DLL MERCURYW.DLL # MERCURYX.DLL MERCURYI.DLL MERCURYB.DLL [Mercury] failfile:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\MERCURY\Mercury\FAILURE.MER&nbsp;&nbsp;&nbsp; # Delivery failure notification template confirmfile:&nbsp;&nbsp; C:\MERCURY\Mercury\CONFIRM.MER&nbsp;&nbsp;&nbsp; # Delivery confirmation template aliasfile:&nbsp;&nbsp;&nbsp;&nbsp; C:\MERCURY\Mercury\ALIAS.MER&nbsp;&nbsp;&nbsp; # System-wide alias file synfile:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\MERCURY\Mercury\SYNONYM.MER&nbsp;&nbsp;&nbsp; # User synonym database listfile:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\MERCURY\Mercury\LISTS.MER&nbsp;&nbsp;&nbsp; # List of lists logfile:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D:\Mlogs\Syslog.log&nbsp;&nbsp;&nbsp; # Traffic logging file logwidth:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 30&nbsp;&nbsp;&nbsp; # Width of address fields in logfile retpath:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # Do/Don't use 'return-path' for errors maxhops:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 30&nbsp;&nbsp;&nbsp; # Used to detect mailing loops gullible:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # If NZ, don't validate 'From' fields bitnethost:&nbsp;&nbsp;&nbsp; cunyvm.cuny.edu&nbsp;&nbsp;&nbsp; # Relay host for '.bitnet' rewrites poll:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp; # Seconds between queue polling cycles scratch:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D:\Mlogs\Scratch&nbsp;&nbsp;&nbsp; # Where we can write temp files returnlines:&nbsp;&nbsp; 15&nbsp;&nbsp;&nbsp; # How many lines of failed messages to return postmaster:&nbsp;&nbsp;&nbsp; dwi&nbsp;&nbsp;&nbsp; # NetWare UIC of postmaster broadcast:&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # Yes, we want broadcast notifications, but receipts:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # ... no broadcasts for receipt confirmations PM_notify:&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # Do/Don't send errors to the postmaster change_owner:&nbsp; 1&nbsp;&nbsp;&nbsp; # Change message ownership to recipient auto_tzone:&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # If NZ, obtain timezone information from OS LogLevel:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 15&nbsp;&nbsp;&nbsp; # System message reporting level LogMax:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp; # Maximum number of system messages to store RetryPeriod:&nbsp;&nbsp; 30&nbsp;&nbsp;&nbsp; # Period between job retries (minutes) MaxRetries:&nbsp;&nbsp;&nbsp; 16&nbsp;&nbsp;&nbsp; # Maximum number of times a job can fail TwoPasses:&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # If NZ, process submission queue in 2 passes Autoaddress:&nbsp;&nbsp; 7&nbsp;&nbsp;&nbsp; # If NZ, auto-generate user addresses based on name Daily_exit:&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # If NZ, auto-restart each day after maintenance No_Areply:&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # If NZ, disable automatic replies system-wide Alt_Forward:&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # If NZ, allow alternate forwarding specification Maint_hour:&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp; # Hour for daily maintenance (24-hour clock) Maint_min:&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # Minute for daily maintenance Retry_Mode:&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # If NZ, use progressive backoff for queue retries Local_DSNs:&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # If NZ generate Delivery Status for local users only DSN_time1:&nbsp;&nbsp;&nbsp;&nbsp; 10800&nbsp;&nbsp;&nbsp; # Seconds deferred before first DSN is sent DSN_time2:&nbsp;&nbsp;&nbsp;&nbsp; 86400&nbsp;&nbsp;&nbsp; # Seconds deferred before second DSN is sent DSN_time3:&nbsp;&nbsp;&nbsp;&nbsp; 259200&nbsp;&nbsp;&nbsp; # Seconds deferred before third DSN is sent Host_in_title: 0&nbsp;&nbsp;&nbsp; # If NZ, show hostname in system tray and taskbar Lingering:&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # Enable or disable 'lingering mailboxes' Linger_Timeout: 60&nbsp;&nbsp; # Seconds before a lingering mailbox is shut down Alert_Host:&nbsp;&nbsp;&nbsp; notify.pmail.com&nbsp;&nbsp;&nbsp; # Host to check for licensee advisories Alert_Interval: 720&nbsp;&nbsp; # Frequency in minutes (min 240) for checks Alert_Flags:&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # Flags controlling advisory checks Alert_Users:&nbsp;&nbsp; dwi&nbsp;&nbsp;&nbsp; # Local users to receive advisories [MercuryC] Host : smtp.ntltelewestbusiness.co.uk Failfile : C:\MERCURY\Mercury\FAILURE.MER Poll : 10 Scratch : C:\MERCURY\Mercury ReturnLines : 15 Timeout : 240 ESMTP : 1 POP3_Auth : 0 Logfile : d:\Mlogs\logs\smtprelayclient Log_Verbose : 1 Session_logging : d:\Mlogs\logs\smtprelayclient Session_logmode : 1 [MercuryE] HELO : Baylis Mail Server Session_logging : d:\mlogs\SMTPCSD Session_logmode : 0 Poll : 15 Timeout : 60 Nameservers : 10.51.4.220 Logfile : d:\mlogs\SMTPCL.log Log_Verbose : 0 DNS_Timeout : 20 DNS_Retries : 4 Transcripts : 1 MaxThreads : 10 [MercuryD] Scratch : C:\MERCURY\Mercury Timeout : 100 Poll : 30 Session_logging : d:\Mlogs\POPCSL.log Session_logmode : 0 [MercuryS] Debug : 1 Logfile : D:\Mlogs\MERCURYS.LOG Timeout : 60 Relay : 0 Strict_Relay : 0 8BitMime : 1 Allow_Illegals : 0 SMTP_Authentication : 1 Auth_File : smtp_auth.txt Session_logging : D:\Mlogs\SMTPServ Session_logmode : 1 Compliance_Settings : 944 Maximum_Failed_Rcpts : 15 Max_Relay_Attempts : 4 SSL_Mode : 0 ST_Blacklisting : 288 No_VRFY : 0 SMTP_ConnFlags : 0 Compliance_Exceptions : restrictOK.txt [MercuryP] Scratch : C:\MERCURY\Mercury Logfile : d:\Mlogs\pop3s.log Stack : 32768 Mark_Read : 1 SSL_Mode : 0 Login_Disabled : 0 UIDL_nul_list : 1 New_UIDs : 0 No_NUL_passwords : 0 Session_logging : d:\Mlogs\POP3SSD Session_logmode : 0 Timeout : 60 [MercuryX] Cmd_Wait: 1 IE4_Dialling: 0 Use_ETRN: 0 Clients_only: 0 Drain_queues: 1 Sunday: 0000,0400,5000,0,0,0 Monday: 0000,0400,5000,0,0,0 Tuesday: 0000,0400,5000,0,0,0 Wednesday: 0000,0400,5000,0,0,0 Thursday: 0000,0400,5000,0,0,0 Friday: 0000,0400,5000,0,0,0 Saturday: 0000,0400,5000,0,0,0 [Domains] mydomains [Maiser] Maiser:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Maiser&nbsp;&nbsp; # 'Username' of mail server account Helpfile:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\MERCURY\Mercury\MAISER.HLP&nbsp;&nbsp; # Help sent on failed maiser requests Lookupfile:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\MERCURY\Mercury\MAISER.LKP&nbsp;&nbsp; # Format file for the 'lookup' command Send_dir:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\MERCURY\Mercury\SENDABLE&nbsp;&nbsp; # Directory for the 'send' command Logfile:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D:\Mlogs\MAISER.LOG&nbsp;&nbsp; # Mail server log file Notify:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\MERCURY\Mercury\TMP&nbsp;&nbsp; # Dir. for pending 'notify' commands NoList:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; N&nbsp;&nbsp; # If 'Y', disable the 'list' command Local_only:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Y&nbsp;&nbsp; # If 'Y', local 'notify' commands only [MercuryH] Logfile&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :&nbsp;&nbsp;&nbsp;&nbsp; C:\MERCURY\Logs\MERCURYH.LOG # Addressbook : <A href="file://clio/SYS/SYSTEM/MERCURY/PH.PMR">\\CLIO\SYS\SYSTEM\MERCURY\PH.PMR</A> # MOTD : <A href="file://clio/SYS/SYSTEM/MERCURY/PH-MOTD.TXT">\\CLIO\SYS\SYSTEM\MERCURY\PH-MOTD.TXT</A> # Administrator : <A href="mailto:postmaster@clio.pmail.gen.nz">postmaster@clio.pmail.gen.nz</A> Timeout : 30 [MercuryI] Scratch : C:\MERCURY\SCRATCH Logfile : d:\Mlogs\imapl.log Timeout : 120 Server_Port : 143 SSL_Port: 993 Charset : ISO-8859-1 Session_logging : d:\Mlogs\imapsd Session_logmode : 0 Idle_Timeout : 1800 SSL_Mode : 0 Login_Disabled : 0 No_NUL_passwords : 1 [MercuryB] Scratch : C:\MERCURY\SCRATCH Timeout : 120 Server_Port : 81 Idle_Timeout : 1800 URL_Base : 10.51.4.10 SSL_Mode : 0 Alt_Server_Port : 443 [Groups] [Rewrite] [Statistics] StatFlags:&nbsp;&nbsp;&nbsp; 16&nbsp; # Statistical reporting settings STF_Hours:&nbsp;&nbsp;&nbsp; 24&nbsp; # How often to write stat log files STM_Hours:&nbsp;&nbsp;&nbsp; 24&nbsp; # How often to e-mail stat log files &nbsp; &nbsp;

Thomas R. Stephenson

posted Aug 9 '10 at 3:43 pm

> I've searched the forum for an answer but can't find one so hopefully someone can point me in the right direction!
>
> I have placed an areply.pm file in a user's mailbox and it works fine for local mail. However, all non-local mail errors with:
>
> ---
>
> The attached message has failed delivery and has been referred to you as postmaster. The following error report or reports were given to explain the problem:
>
> *** leizure@leizure.force9.co.uk
> 550 relaying mail to leizure.force9.co.uk is not allowed
> ---
>
> I did have 'strict local relaying' ticked but I've now removed that and just have 'do not permit SMTP relaying of local mail'.

Strict MUST be selected if the server is connected to the internet of else you will be an open relay. The spammers will find your server and it will be blacklisted shortly afterwords.

>
> Therefore, as I understand the help file, any locally sent email to a non-local address will be accepted.

Any mail that has a domain portion matching the domains of you server will be allowed to relay.
>
> The email is being sent from the local system using the user's email address as the FROM address so why does it not send?

Because you do not have any domains set.

>
> Config is: 4.72 ::
>

Mercury.ini info trimmed where not material to the problem.

> [General]
> myname: mydomain # Canonical name for this server

Should be a real domain name here. This is the domain used by the postmaster when sending error messages.

> timezone: +0000 # Time Zone to add to date fields
> file_api: 1 # Use the file api instead of queues
> mailqueue: C:\MERCURY\QUEUE # Where mail should be put for delivery
> smtpqueue: C:\MERCURY\QUEUE # Where the SMTP client should look for mail
> newmail_path: C:\MERCURY\MAIL\~N # Where to find the users' WinPMail mailboxes.
>
> [Protocols]
> MERCURYS.DLL
> MERCURYP.DLL
> # MERCURYE.DLL
> MERCURYC.DLL

Sending via MercuryC

> MERCURYD.DLL
> # MERCURYH.DLL
> # MERCURYF.DLL
> MERCURYW.DLL
> # MERCURYX.DLL
> MERCURYI.DLL
> MERCURYB.DLL
>
> [Mercury]
>
> [MercuryC]
> Host : smtp.ntltelewestbusiness.co.uk

This is the domain name of the relay host? I cannot connect to port 25 of this host.

> Failfile : C:\MERCURY\Mercury\FAILURE.MER
> Poll : 10
> Scratch : C:\MERCURY\Mercury
> ReturnLines : 15
> Timeout : 240
> ESMTP : 1
> POP3_Auth : 0
> Logfile : d:\Mlogs\logs\smtprelayclient
> Log_Verbose : 1
> Session_logging : d:\Mlogs\logs\smtprelayclient
> Session_logmode : 1
>
> [MercuryS]
> Debug : 1
> Logfile : D:\Mlogs\MERCURYS.LOG
> Timeout : 60
> Relay : 0
> Strict_Relay : 0
> 8BitMime : 1
> Allow_Illegals : 0
> SMTP_Authentication : 1
> Auth_File : smtp_auth.txt
> Session_logging : D:\Mlogs\SMTPServ
> Session_logmode : 1
> Compliance_Settings : 944
> Maximum_Failed_Rcpts : 15
> Max_Relay_Attempts : 4
> SSL_Mode : 0
> ST_Blacklisting : 288
> No_VRFY : 0
> SMTP_ConnFlags : 0
> Compliance_Exceptions : restrictOK.txt
>
> [Domains]
> mydomains

You must have some local domains set. This should look like

server : server
server : my.domain.name
server : [<my fixed IP address>]

Here's what I have on this system. There is no bracketed IP address since I do not have a fixed IP address for this laptop.

[Domains]
tstephenson: tstephenson
tstephenson: mail.tstephenson.com
tstephenson: lap.tstephenson.com

&gt; I've searched the forum for an answer but can't find one so hopefully someone can point me in the right direction! &gt; &gt; &nbsp;I have placed an areply.pm file in a user's mailbox and it works fine for local mail. However, all non-local mail errors with: &gt; &gt; --- &gt; &gt; &nbsp;The attached message has failed delivery and has been referred to you as postmaster. The following error report or reports were given to explain the problem: &gt; &gt; &nbsp;&nbsp; *** leizure@leizure.force9.co.uk &gt; &nbsp;&nbsp; 550 relaying mail to leizure.force9.co.uk is not allowed &gt; --- &gt; &gt; I did have 'strict local relaying' ticked but I've now removed that and just have 'do not permit SMTP relaying of local mail'. Strict MUST be selected if the server is connected to the internet of else you will be an open relay.&nbsp; The spammers will find your server and it will be blacklisted shortly afterwords. &gt; &gt; Therefore, as I understand the help file, any locally sent email to a non-local address will be accepted. Any mail that has a domain portion matching the domains of you server will be allowed to relay. &nbsp; &gt; &gt; The email is being sent from the local system using the user's email address as the FROM address so why does it not send? Because you do not have any domains set. &gt; &gt; Config is: 4.72 :: &gt; Mercury.ini info trimmed where not material to the problem. &gt; [General] &gt; myname:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mydomain # Canonical name for this server Should be a real domain name here.&nbsp; This is the domain used by the postmaster when sending error messages. &gt; timezone:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +0000&nbsp;&nbsp;&nbsp; # Time Zone to add to date fields &gt; file_api:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # Use the file api instead of queues &gt; mailqueue:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\MERCURY\QUEUE&nbsp;&nbsp;&nbsp; # Where mail should be put for delivery &gt; smtpqueue:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\MERCURY\QUEUE&nbsp;&nbsp;&nbsp; # Where the SMTP client should look for mail &gt; newmail_path:&nbsp;&nbsp;&nbsp; C:\MERCURY\MAIL\~N&nbsp;&nbsp;&nbsp; # Where to find the users' WinPMail mailboxes. &gt; &gt; [Protocols] &gt; MERCURYS.DLL &gt; MERCURYP.DLL &gt; # MERCURYE.DLL &gt; MERCURYC.DLL Sending via MercuryC &gt; MERCURYD.DLL &gt; # MERCURYH.DLL &gt; # MERCURYF.DLL &gt; MERCURYW.DLL &gt; # MERCURYX.DLL &gt; MERCURYI.DLL &gt; MERCURYB.DLL &gt; &gt; [Mercury] &gt; &gt; [MercuryC] &gt; Host : smtp.ntltelewestbusiness.co.uk This is the domain name of the relay host?&nbsp; I cannot connect to port 25 of this host. &gt; Failfile : C:\MERCURY\Mercury\FAILURE.MER &gt; Poll : 10 &gt; Scratch : C:\MERCURY\Mercury &gt; ReturnLines : 15 &gt; Timeout : 240 &gt; ESMTP : 1 &gt; POP3_Auth : 0 &gt; Logfile : d:\Mlogs\logs\smtprelayclient &gt; Log_Verbose : 1 &gt; Session_logging : d:\Mlogs\logs\smtprelayclient &gt; Session_logmode : 1 &gt; &gt; [MercuryS] &gt; Debug : 1 &gt; Logfile : D:\Mlogs\MERCURYS.LOG &gt; Timeout : 60 &gt; Relay : 0 &gt; Strict_Relay : 0 &gt; 8BitMime : 1 &gt; Allow_Illegals : 0 &gt; SMTP_Authentication : 1 &gt; Auth_File : smtp_auth.txt &gt; Session_logging : D:\Mlogs\SMTPServ &gt; Session_logmode : 1 &gt; Compliance_Settings : 944 &gt; Maximum_Failed_Rcpts : 15 &gt; Max_Relay_Attempts : 4 &gt; SSL_Mode : 0 &gt; ST_Blacklisting : 288 &gt; No_VRFY : 0 &gt; SMTP_ConnFlags : 0 &gt; Compliance_Exceptions : restrictOK.txt &gt; &gt; [Domains] &gt; mydomains You must have some local domains set.&nbsp; This should look like server : server server : my.domain.name server : [&lt;my fixed IP address&gt;] Here's what I have on this system.&nbsp; There is no bracketed IP address since I do not have a fixed IP address for this laptop. [Domains] tstephenson: tstephenson tstephenson: mail.tstephenson.com tstephenson: lap.tstephenson.com

Leizure

posted Aug 24 '10 at 6:54 pm

I'm disappointed that I haven't had loads of answers to this ![:'(]

Any takers?

Dave.

I'm disappointed that I haven't had loads of answers to this ![:'(] Any takers? &nbsp; Dave.

Thomas R. Stephenson

posted Aug 24 '10 at 7:25 pm

I'm disappointed that I haven't had loads of answers to this !
Any takers?

Was there something wrong with my answer???

<blockquote>I'm disappointed that I haven't had loads of answers to this !<img src="http://community.pmail.com/emoticons/emotion-9.gif" alt="Crying">Any takers?</blockquote>Was there something wrong with my answer???&nbsp;

Rolf Lindby

posted Aug 24 '10 at 7:26 pm

*** leizure@leizure.force9.co.uk
550 relaying mail to leizure.force9.co.uk is not allowed

Hm... Isn't that a 550 reply from the receiving SMTP server rather than from Mercury? Autoreplies generated by the system should always be allowed.

/Rolf

<blockquote>&nbsp;&nbsp; *** <a href="mailto:leizure@leizure.force9.co.uk">leizure@leizure.force9.co.uk</a> &nbsp;&nbsp; 550 relaying mail to leizure.force9.co.uk is not allowed</blockquote>Hm... Isn't that a 550 reply from the receiving SMTP server rather than from Mercury? Autoreplies generated by the system should always be allowed./Rolf

Leizure

posted Aug 31 '10 at 4:57 pm

[quote user="Thomas R. Stephenson"]

I'm disappointed that I haven't had loads of answers to this !

Any takers?

Was there something wrong with my answer???

[/quote]

Sorry Thomas, I rely on the RSS feed to let me know when there's an update - obviously it doesn't work for replies to logged problems!

I'll check your reply, thanks.

[quote user="Thomas R. Stephenson"] <BLOCKQUOTE> I'm disappointed that I haven't had loads of answers to this !<IMG alt=Crying src="http://community.pmail.com/emoticons/emotion-9.gif" mce_src="http://community.pmail.com/emoticons/emotion-9.gif"> Any takers?</BLOCKQUOTE> Was there something wrong with my answer??? &nbsp; [/quote] Sorry Thomas, I rely on the RSS feed to&nbsp;let me know when there's an update - obviously&nbsp;it doesn't work for replies to logged problems! I'll check your reply, thanks.&nbsp;

Leizure

posted Aug 31 '10 at 5:19 pm

I have checked the ini file as per Thomas' suggestions and turned STRICT back on.

The domains are setup correctly with domain names, I had just removed them for this post - however I didn't have the server: server set up as the first line, it was the third. I've changed it just in case it matters.

The smtp.ntltelewestbusiness.co.uk address is correct and it is using port 25. I think it may only be possible to connect to it on their broadband connection (known IP).

So I'll test it now I've swapped teh domains around and hope for the best.

Thanks

Dave.

I have checked the ini file as per Thomas' suggestions and turned STRICT back on. The domains are setup correctly with domain names, I had just removed them for this post - however I didn't have the server: server set up as the first line, it was the third. I've changed it just in case it matters. The smtp.ntltelewestbusiness.co.uk address is correct and it is using port 25. I think it may only be possible to connect to it on their broadband connection (known IP). So I'll test it now I've swapped teh domains around and hope for the best. &nbsp;Thanks Dave.

Leizure

posted Aug 31 '10 at 6:01 pm

No change - still get the 550 error back.

I tried sending an email from Mercury and that went through OK.

I note that Rolf has questioned that the error might be with the ISP, but if that is the case why would it only block autoreplies and not all mail?

I've looked through the logs but I'm unsure which one holds the key information for this error, can anyone advise?

Dave.

No change - still get the 550 error back. I tried sending an email from Mercury and that went through OK. I note that Rolf has questioned that the error might be with the ISP, but if that is the case why would it only block autoreplies and not&nbsp; all mail? I've looked through the logs but I'm unsure which one holds the key information for this error, can anyone advise? &nbsp; Dave.

Rolf Lindby

posted Aug 31 '10 at 6:26 pm

If the autoreplies to leizure.force9.co.uk are refused by your ISP's SMTP server you will probably have to contact your ISP's helpdesk and ask why they do that.

/Rolf

If the autoreplies to leizure.force9.co.uk are refused by your ISP's SMTP server you will probably have to contact your ISP's helpdesk and ask why they do that. /Rolf

Thomas R. Stephenson

posted Aug 31 '10 at 6:39 pm

No change - still get the 550 error back.
I tried sending an email from Mercury and that went through OK.
I note that Rolf has questioned that the error might be with the ISP,
but if that is the case why would it only block autoreplies and not
all mail?
I've looked through the logs but I'm unsure which one holds the key information for this error, can anyone advise?

Without looking at the MercuryC session log I am just guessing but the autoreply should be using the same MAIL FROM: address as the normal sending from that user and so if they are blocking the automatic reply from a user that should also block that user when sent via MercuryC. You really need to pass a session log to the ISP and ask them why this is happening.

<blockquote>No change - still get the 550 error back.I tried sending an email from Mercury and that went through OK.I note that Rolf has questioned that the error might be with the ISP, but if that is the case why would it only block autoreplies and not&nbsp; all mail?I've looked through the logs but I'm unsure which one holds the key information for this error, can anyone advise?</blockquote>Without looking at the MercuryC session log I am just guessing but the autoreply should be using the same MAIL FROM: address as the normal sending from that user and so if they are blocking the automatic reply from a user that should also block that user when sent via MercuryC.&nbsp; You really need to pass a session log to the ISP and ask them why this is happening.&nbsp;&nbsp;

Leizure

posted Aug 31 '10 at 7:28 pm

OK, I've got a session log:

17:20:55.953: --- Tue Aug 31 17:20:55 2010 ---
17:20:55.953: Connect to 'smtp.ntltelewestbusiness.co.uk', timeout 240.
17:20:57.015: >> 220 ESMTP server ready<cr><lf>
17:20:57.015: << EHLO baylisvauxhall.co.uk<cr><lf>
17:20:57.031: >> 250-aamtaout04-winn.ispmail.ntl.com<cr><lf>
17:20:57.031: >> 250-HELP<cr><lf>
17:20:57.031: >> 250-XREMOTEQUEUE<cr><lf>
17:20:57.031: >> 250-ETRN<cr><lf>
17:20:57.031: >> 250-PIPELINING<cr><lf>
17:20:57.031: >> 250-DSN<cr><lf>
17:20:57.031: >> 250-8BITMIME<cr><lf>
17:20:57.031: >> 250 SIZE 15728640<cr><lf>
17:20:57.031: << MAIL FROM:<> SIZE=1015<cr><lf>
17:20:57.046: >> 250 Sender <> and extensions (SIZE=1015) Ok<cr><lf>
17:20:57.062: << RCPT TO:<leizure@leizure.force9.co.uk><cr><lf>
17:20:57.109: >> 550 relaying mail to leizure.force9.co.uk is not allowed<cr><lf>
17:20:57.109: << QUIT<cr><lf>
17:20:57.156: >> 221 aamtaout04-winn.ispmail.ntl.com ESMTP server closing connection<cr><lf>
17:20:57.156: --- Connection closed normally at Tue Aug 31 17:20:57 2010. ---
17:20:57.156:

As you can see there's no FROM address so that's obviously why it's rejected. This now begs the question - why is there no address?

However, on local replies there's definately a from address, as Thomas said, from the person whos autoreply is being processed.

Dave.

OK, I've got a session log: 17:20:55.953: --- Tue Aug 31 17:20:55 2010 --- 17:20:55.953: Connect to 'smtp.ntltelewestbusiness.co.uk', timeout 240. 17:20:57.015: &gt;&gt; 220 ESMTP server ready&lt;cr&gt;&lt;lf&gt; 17:20:57.015: &lt;&lt; EHLO baylisvauxhall.co.uk&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250-aamtaout04-winn.ispmail.ntl.com&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250-HELP&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250-XREMOTEQUEUE&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250-ETRN&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250-PIPELINING&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250-DSN&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250-8BITMIME&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250 SIZE 15728640&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &lt;&lt; MAIL FROM:&lt;&gt; SIZE=1015&lt;cr&gt;&lt;lf&gt; 17:20:57.046: &gt;&gt; 250 Sender &lt;&gt; and extensions (SIZE=1015) Ok&lt;cr&gt;&lt;lf&gt; 17:20:57.062: &lt;&lt; RCPT TO:&lt;<A href="mailto:leizure@leizure.force9.co.uk%3E%3Ccr%3E%3Clf" mce_href="mailto:leizure@leizure.force9.co.uk%3E%3Ccr%3E%3Clf">leizure@leizure.force9.co.uk&gt;&lt;cr&gt;&lt;lf</A>&gt; 17:20:57.109: &gt;&gt; 550 relaying mail to leizure.force9.co.uk is not allowed&lt;cr&gt;&lt;lf&gt; 17:20:57.109: &lt;&lt; QUIT&lt;cr&gt;&lt;lf&gt; 17:20:57.156: &gt;&gt; 221 aamtaout04-winn.ispmail.ntl.com ESMTP server closing connection&lt;cr&gt;&lt;lf&gt; 17:20:57.156: --- Connection closed normally at Tue Aug 31 17:20:57 2010. --- 17:20:57.156: As you can see there's no FROM address so that's obviously why it's rejected. This now begs the question - why is there no address? However, on local replies there's definately a from address, as Thomas said, from the person whos autoreply is being processed. Dave.

Thomas R. Stephenson

posted Aug 31 '10 at 8:09 pm

OK, I've got a session log:
17:20:55.953: --- Tue Aug 31 17:20:55 2010 ---
17:20:55.953: Connect to 'smtp.ntltelewestbusiness.co.uk', timeout 240.
17:20:57.015: >> 220 ESMTP server ready<cr><lf>
17:20:57.015: << EHLO baylisvauxhall.co.uk<cr><lf>
17:20:57.031: >> 250-aamtaout04-winn.ispmail.ntl.com<cr><lf>
17:20:57.031: >> 250-HELP<cr><lf>
17:20:57.031: >> 250-XREMOTEQUEUE<cr><lf>
17:20:57.031: >> 250-ETRN<cr><lf>
17:20:57.031: >> 250-PIPELINING<cr><lf>
17:20:57.031: >> 250-DSN<cr><lf>
17:20:57.031: >> 250-8BITMIME<cr><lf>
17:20:57.031: >> 250 SIZE 15728640<cr><lf>
17:20:57.031: << MAIL FROM:<> SIZE=1015<cr><lf>
17:20:57.046: >> 250 Sender <> and extensions (SIZE=1015) Ok<cr><lf>
17:20:57.062: << RCPT TO:<leizure@leizure.force9.co.uk><cr><lf>
17:20:57.109: >> 550 relaying mail to leizure.force9.co.uk is not allowed<cr><lf>
17:20:57.109: << QUIT<cr><lf>
17:20:57.156: >> 221 aamtaout04-winn.ispmail.ntl.com ESMTP server closing connection<cr><lf>
17:20:57.156: --- Connection closed normally at Tue Aug 31 17:20:57 2010. ---
17:20:57.156:
As you can see there's no FROM address so that's obviously why it's
rejected. This now begs the question - why is there no address?
However, on local replies there's definately a from address, as Thomas said, from the person whos autoreply is being processed.

The SMTP <> MAIL FROM: address is the server to server address and your server is obviously not allowed to relay. MercuryC cannot even make an authenticated connection since this server does not use the ESMTP AUTH command. Now you really need to talk to the ISP since all mail from the server to anyone other than a local user at the ISP is going to be bounced. This is a real problem since any bounced mail to MercuryS from the outside world will also be rejected as relaying.

<blockquote>OK, I've got a session log:17:20:55.953: --- Tue Aug 31 17:20:55 2010 --- 17:20:55.953: Connect to 'smtp.ntltelewestbusiness.co.uk', timeout 240. 17:20:57.015: &gt;&gt; 220 ESMTP server ready&lt;cr&gt;&lt;lf&gt; 17:20:57.015: &lt;&lt; EHLO baylisvauxhall.co.uk&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250-aamtaout04-winn.ispmail.ntl.com&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250-HELP&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250-XREMOTEQUEUE&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250-ETRN&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250-PIPELINING&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250-DSN&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250-8BITMIME&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &gt;&gt; 250 SIZE 15728640&lt;cr&gt;&lt;lf&gt; 17:20:57.031: &lt;&lt; MAIL FROM:&lt;&gt; SIZE=1015&lt;cr&gt;&lt;lf&gt; 17:20:57.046: &gt;&gt; 250 Sender &lt;&gt; and extensions (SIZE=1015) Ok&lt;cr&gt;&lt;lf&gt; 17:20:57.062: &lt;&lt; RCPT TO:&lt;<a href="mailto:leizure@leizure.force9.co.uk%3E%3Ccr%3E%3Clf">leizure@leizure.force9.co.uk&gt;&lt;cr&gt;&lt;lf</a>&gt; 17:20:57.109: &gt;&gt; 550 relaying mail to leizure.force9.co.uk is not allowed&lt;cr&gt;&lt;lf&gt; 17:20:57.109: &lt;&lt; QUIT&lt;cr&gt;&lt;lf&gt; 17:20:57.156: &gt;&gt; 221 aamtaout04-winn.ispmail.ntl.com ESMTP server closing connection&lt;cr&gt;&lt;lf&gt; 17:20:57.156: --- Connection closed normally at Tue Aug 31 17:20:57 2010. --- 17:20:57.156: As you can see there's no FROM address so that's obviously why it's rejected. This now begs the question - why is there no address?However, on local replies there's definately a from address, as Thomas said, from the person whos autoreply is being processed.</blockquote>The SMTP &lt;&gt; MAIL FROM: address is the server to server address and your server is obviously not allowed to relay.&nbsp; MercuryC cannot even make an authenticated connection since this server does not use the ESMTP AUTH command.&nbsp; Now you really need to talk to the ISP since all mail from the server to anyone other than a local user at the ISP is going to be bounced.&nbsp; This is a real problem since any bounced mail to MercuryS from the outside world will also be rejected as relaying. &nbsp;

Leizure

posted Sep 1 '10 at 12:17 pm

Problem sorted. I had an alternative ISP so I've change the SMTP to them instead and it's now working OK.

Thanks for your help.

Dave.

Problem sorted. I had an alternative ISP so I've change the SMTP to them instead and it's now working OK. Thanks for your help. Dave.

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history