Patrick Campbell | 28 Apr 20:42 2014

Nullmailer tries to re-send after permanent error 552

Hi,
Looking for some help on how to fix /  work around this issue. We had a cron job trying to send a large e-mail
which was larger than Outlook would allow.

Nullmailer seemed to understand that this is a permanent error, but does not discard the e-mail but instead
tries to re-send it, resulting in an infinite loop:

nullmailer[15486]: smtp: Failed: 552 5.3.4 Message size exceeds fixed maximum message size
nullmailer[2273]: Sending failed:  Permanent error in sending the message
nullmailer[2273]: Delivery complete, 1 message(s) remain.
nullmailer[2273]: Rescanning queue.
nullmailer[2273]: Starting delivery:

--
Patrick Campbell
Website Administrator
International Cruise & Excursions, Inc. (ICE)
Phone 602.896.4729 (x4729)
Cell Phone 602.723.3098
Regid Ichira | 24 Jan 23:30 2012
Picon

Pseudo code included. Is it a small step towards better LSB compliance for sendmail interface?

  Continuing
http://lists.untroubled.org/?list=nullmailer&cmd=threadindex&month=201002&threadid=hobkhempdacmpcpddmbi

  Is this pseudo code a small step towards better lsb compliance for
sendmail interface?

--- sendmail.cc.orig    2012-01-24 23:42:10.000000000 +0200
+++ sendmail.cc 2012-01-25 00:09:35.000000000 +0200
 <at>  <at>  -92,7 +92,11  <at>  <at>  int parseargs()
     if(!setenvelope(o_from))
       return -1;
   if (o_mode && !strcmp(o_mode, "s")) {
-    ferr << "sendmail: option -bs is unsupported" << endl;
+
+    Wait for input on stdin.  What ever 1st line you get
+
+    fstdout << "550 Refuse communication by SMTP commands on stdin/stdoutd" << endl;
+
     return -1;
   }
   return 0;
Jeffrey C. Dege | 8 Jan 18:54 2012
Picon

Is there a "verbose" setting?

I'm trying to set up a new Linux Mint 12.0 install, which by default
installs nullmailer as a forward-only MTA.

I don't need anything other than a forward-only MTA, on this machine, so
I'm trying to get it to work.

First, I'm able to send emails from this machine using smtp-cli - a
command-line smtp forwarder.  So the connectivity is fine, I have the
right smtp hostname, user, password, etc.

My primary concern is getting things configured so that mails sent by
the standard Unix daemons (crond et al.) get sent to an external mail
account that I actually read.

I've installed mutt, to use as a tool for generating the emails.  When I
send an email using mutt, I see it show up
in /var/spool/nullmailer/queue, so I'm pretty sure it's communicating
with nullmailer properly.

So I've been sending emails to the addresses I want to test, and
watching /var/log/mail.log and /var/log/mail.err.

First problem was authentication.  I needed to add username and password
to /etc/nullmailer/remotes.

Second problem was domain names.  This machine doesn't have a meaningful
domain name.  I've been messing about with /etc/mailname and
with /etc/nullmailer/adminaddr, /etc/nullmailer/defaultdomain,
and /etc/nullmailer/me, until the outgoing mails are no longer being
rejected by the smtp server, for unknown domains, whether I send to
(Continue reading)

Thomas A. Moulton | 19 Jul 13:42 2011
Picon

pausetime file

When does the pause time go into effect?

Is the pause time applied to each message or the whole queue?

Like the other control files I assume to set the pause to 15 mins I just 
have a line like:

900

What is the default setting? (no file)

Thanks!
Tom
Steve Litt | 7 Jul 23:37 2011

How to debug nullmailer

Hi all,

I'm running nullmailer on Ubuntu 10.04 LTS, and can't get it to mail, 
and get seemingly infinite error messages. I need to know what steps 
to take to troubleshoot this, and especially how to locate the 
nullmailer queue, which I suspect has some bad stuff in it.

I don't really know how to use nullmailer after going through the info 
on /usr/share/doc/nullmailer and googling.

Here's what happens when I run nullmailer-send as root:

===========================================
Sending failed: Permanent error in sending the message
Starting delivery: protocol: smtp host: mail.a3b3.com file: 
1309464266.3980
smtp: Failed: 550-Verification failed for <slitt <at> mydesk.mydesk>/550-
The mail server could not deliver mail to slitt <at> mydesk.mydesk.  The 
account or domain may not exist, they may be blacklisted, or missing 
the proper dns entries./550 Sender verify failed
===========================================

When I run mailq as root it gives me a long or infinite list of 
messages like this:

===========================================
2011-03-04 22:04:26 798 bytes from <slitt <at> mydesk.mydesk>
  to <slitt <at> mydesk.mydesk>
===========================================

(Continue reading)

Nick Leverton | 29 Apr 19:35 2011

sendtimeout in nullmailer-send only works first time through

Hi,

As per subject line, it seems that the new sendtimeout in 1.05 only
works the first time through.  Second and subsequent times, the timeout
isn't triggered, and smtp only exits when the connection attempt fails.
Notice below that the "Sending timed out" message is only printed first
time in after restart of nullmailer-send.

Apr 29 16:40:15 nullmailer[1934]: Starting delivery: protocol: smtp host: mail.home file: 1304089334.1822
Apr 29 16:41:16 nullmailer[1934]: Sending timed out, killing protocol
Apr 29 16:41:16 nullmailer[1934]: Delivery complete, 1 message(s) remain.
Apr 29 16:42:16 nullmailer[1934]: Rescanning queue.
Apr 29 16:42:16 nullmailer[1934]: Starting delivery: protocol: smtp host: mail.home file: 1304089334.1822
Apr 29 16:45:25 nullmailer[2065]: smtp: Failed: Connect failed
Apr 29 16:45:25 nullmailer[1934]: Sending failed:  Connection timed out
Apr 29 16:45:25 nullmailer[1934]: Delivery complete, 1 message(s) remain.
Apr 29 16:46:25 nullmailer[1934]: Rescanning queue.
Apr 29 16:46:25 nullmailer[1934]: Starting delivery: protocol: smtp host: mail.home file: 1304089334.1822
Apr 29 16:49:35 nullmailer[2066]: smtp: Failed: Connect failed
Apr 29 16:49:35 nullmailer[1934]: Sending failed:  Connection timed out
Apr 29 16:49:35 nullmailer[1934]: Delivery complete, 1 message(s) remain.
Apr 29 16:50:35 nullmailer[1934]: Rescanning queue.
Apr 29 16:50:35 nullmailer[1934]: Starting delivery: protocol: smtp host: mail.home file: 1304089334.1822
Apr 29 16:53:44 nullmailer[2073]: smtp: Failed: Connect failed
Apr 29 16:53:44 nullmailer[1934]: Sending failed:  Connection timed out

This is on Debian using Linux 2.6.32 with glibc 2.7, and 2.6.38 with
glibc 2.11 (but I've also observed it on Fedora 7 and 8, though I no
longer have access to those systems).

(Continue reading)

Philippe LeCavalier | 20 Mar 14:07 2011

Sending with fake cert

Anyone?

Hi I'm trying to switch from msmtp but I can't find any help about
sending to a server that uses a fake cert. in msmtp I had:

tls on tls_certcheck off tls_starttls off

This would allow me to use TLS, turn off startTLS and ignore the fake
cert warning.

How do I do this with nullmailer?
--

-- 
Thanks,
Phil
Philippe LeCavalier | 18 Mar 13:05 2011

Sending with fake cert

Hi I'm trying to switch from msmtp but I can't find any help about
sending to a server that uses a fake cert. in msmtp I had:

tls on tls_certcheck off tls_starttls off

This would allow me to use TLS, turn off startTLS and ignore the fake
cert warning.

How do I do this with nullmailer?
--

-- 
Thanks,
Phil
Martin Williams | 12 Jan 01:51 2011
Picon

smtp failure - unrouteable envelope sender address

Hi,

I wish to use nullmailer to sweep locally (system) generated mail up  
to my ISP's smart host relay, for forwarding. Host/users do not and  
will not belong to a valid mail domain. The host is a small headless  
server.

Creating the 'adminaddr' control file will deal with local recipient  
addresses nicely in these circumstances, i.e. the mail will go  
'somewhere sensible'. But I find that I will need to deal with the  
envelope sender in similar manner. At present the relay rejects any  
mail offered to it, as the sender address is unrouteable (typically root <at> xxx.xxx 
). I have no control over the relay.

I think that 'nullmailer-queue' could be easily adapted to read an  
'adminaddr-sender' control file and apply the same logic to the sender  
address as is currently applied to recipient addresses. That would  
solve the issue for me.

But perhaps I am missing something obvious. Is there a solution/ 
configuration already available that I have missed ?

Thanks for any help.

Martin Williams
Bruce Guenter | 12 Nov 15:54 2010

Source repositories moved to github

Hi.

FYI I have just completed uploading all my source repositories (well, at
least all the git ones, which is almost everything public) over to
github.  You can find them at:

	https://github.com/bruceg

--

-- 
Bruce Guenter <bruce <at> untroubled.org>                http://untroubled.org/
Nils Toedtmann | 4 May 16:35 2010
Picon

Several target addresses in adminaddr?

Hi there,

how can i send rootmail to multiple mail addresses using nullmailer? Can
i enter several addresses into adminaddr?

Cheers, /nils.

PS: We are using nullmailer on all our servers which are not meant to be
MTAs. Thank you for developing this useful piece!


Gmane